Event Date Best Practice

The Event Date is key when it is necessary to differentiate between multiple occurrences of the same event for the same recipient.

For example, if we created an Order Placed event, a recipient will be included in the segment when they place an order.

If a timestamp is used based on the Engine Order Date then the following scenarios can be avoided:

• The same recipient being included in the segment a further time based on a single first purchase.
• The same recipient being included in the same segment for all their future orders.

When a recipient first places an order, they are included in the segment with the Order Date being used as the Event Date (inserted into SQL Campaign Recipient Event table). The next time the tool polls it will exclude this recipient because it has already processed the event for that Order Date.

When the recipient places a second order, the Engine Orders table and Order Date will be updated in the nightly data upload. Because this new Order Date does not exist in the Campaign Recipient Event table (for this individual recipient), the recipient will be included in the segment again, and a trigger action can be applied - for example to re-enter a specified campaign track.

• When in Segment
  • Event Date Best Practice